Description:

closes #179

Issue raised on mobile application using the omni-text-field component.

Note this issue will not occur on more modern devices as these devices will have a "next" button which will focus the next input component vs a "enter" button.

Screenshots (if appropriate):

For the testing of this use case it was done using developer tools in the chrome browser this is not close to a real world scenario although the issue can be demonstrated

Values are typed in a the omni-text-field component and then the enter key is pressed on the keyboard.

Before

After

IPhone Tests

Before

After

All Submissions:

• I have followed the contribution guidelines for this project.
• I have checked to ensure there aren't other open Pull Requests for the same update/change.

Changes to Core Features:

• I have added an explanation of what my changes do and why I would like to include them.
• I have written new tests for my core changes, as applicable.
• I have successfully ran tests with my changes locally.
• I have added/updated docs, as applicable.